Problem Note 57995: The DATE11. informat incorrectly returns a missing value in the SAS® LASR™ Analytic Server
 |  |  |  |
The DATE11. informat incorrectly returns a missing value when it is specified in a program that runs in the SAS LASR Analytic Server. This problem occurs when the code is submitted using a DATA step, the SCORE statement in PROC IMSTAT or the UPDATE statement in PROC IMSTAT. The problem does not occur when the in-memory table is transferred to the client before performing the computation.
To circumvent the problem, use the ANYDTDTE11. informat instead of the DATE11. informat.
In the example below, the first DATA step runs on the client and Date1 is correct. The DSACCEL=ANY system option causes the second DATA step to run in memory. As a result, Date2 is incorrectly set to a missing value. The workaround is used to create Date3.
libname mylasr sasiola start=yes;
data mylasr.test1;
Date1=input("15-jul-2015", date11.);
output;
run;
proc print;
format Date1 z8.0;
run;
options dsaccel=any msglevel=i;
data mylasr.test2;
set mylasr.test1;
Date2=input("16-jul-2015", date11.);
Date3=input("17-jul-2015", anydtdte11.);
run;
proc print data=mylasr.test2;
run;
libname mylasr clear;
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS LASR Analytic Server | Solaris for x64 | 9.4 TS1M2 | 9.4 TS1M4 |
| Linux for x64 | 9.4 TS1M2 | 9.4 TS1M4 | ||
| 64-bit Enabled Solaris | 9.4 TS1M2 | 9.4 TS1M4 | ||
| 64-bit Enabled AIX | 9.4 TS1M2 | 9.4 TS1M4 | ||
| Microsoft® Windows® for x64 | 9.4 TS1M2 | 9.4 TS1M4 | ||
The DATE11. informat incorrectly returns a missing value when it is used in code that is executed in the LASR Analytic Server.
| Type: | Problem Note |
| Priority: | medium |
| Topic: | Analytics ==> analytics SAS Reference ==> Procedures ==> IMSTAT |
| Date Modified: | 2016-07-06 10:43:18 |
| Date Created: | 2016-04-04 14:28:18 |